build(deps): update sentry-sdk[fastapi] requirement from >=2.66.1 to >=2.68.0 in /backend - #188

Sourced from sentry-sdk[fastapi]'s releases.

2.68.0

Important

• We're making enable_logs and enable_metrics no-op with this release (#7177), and they'll be dropped in the next major.

  Previously, enable_logs also controlled automatic logs collection from the logging and Loguru integrations. These integrations now get an integration-level capture_sentry_logs boolean option to allow for more control over the auto-collection. These options are False by default, i.e., nothing is auto-collected without your explicit opt-in.

  Action Needed

  If you had enable_logs set to True:

  • If you were using the sentry_sdk.logger.X API, no action necessary, the API will just work.
  • If you were auto-collecting logs from either LoggingIntegration or LoguruIntegration, the auto-collection will be turned off in this release. You can switch auto-collection on explicitly with:

  import sentry_sdk
  from sentry_sdk.integrations.logging import LoggingIntegration
  from sentry_sdk.integrations.loguru import LoguruIntegration
  sentry_sdk.init(
  integrations=[
  LoggingIntegration(capture_sentry_logs=True),
  LoguruIntegration(capture_sentry_logs=True),
  ],
  )

  If you had enable_logs set to False:

  • If you were using it to gate usages of the sentry_sdk.logger.X API, you'll need to remove the calls entirely or define a before_send_log callback to filter out unwanted logs.

  If you has enable_metrics set to False:

  • Any metrics emitted using the metrics API will be emitted. You'll need to drop them in a before_send_metric or remove the calls to the API.

  Why We're Doing This

  We recognize this is a disruptive change for some folks and want to make it clear this is a one-off. We're removing the options because they were an unnecessary hurdle that one had to jump through to be able to use logs and metrics, and it was confusing why the logging API would not just work on its own. On the other hand, we wanted to give you more fine-grained control over automatic collection.

New Features ✨

Other

• Set the segment source on the scope for NoOpStreamedSpan by @​alexander-alderman-webb in #7163
• Remove early return for NoOpStreamedSpan in set_transaction_name() by @​alexander-alderman-webb in #7164
• Set the segment name on the scope with NoOpStreamedSpan by @​alexander-alderman-webb in #7162

Bug Fixes 🐛

• (batcher) Add global flush trigger based on the span number by @​alexander-alderman-webb in #7150

Internal Changes 🔧

... (truncated)

Sourced from sentry-sdk[fastapi]'s changelog.

2.68.0

Important

• We're making enable_logs and enable_metrics no-op with this release (#7177), and they'll be dropped in the next major.

  Previously, enable_logs also controlled automatic logs collection from the logging and Loguru integrations. These integrations now get an integration-level capture_sentry_logs boolean option to allow for more control over the auto-collection. These options are False by default, i.e., nothing is auto-collected without your explicit opt-in.

  Action Needed

  If you had enable_logs set to True:

  • If you were using the sentry_sdk.logger.X API, no action necessary, the API will just work.
  • If you were auto-collecting logs from either LoggingIntegration or LoguruIntegration, the auto-collection will be turned off in this release. You can switch auto-collection on explicitly with:

  import sentry_sdk
  from sentry_sdk.integrations.logging import LoggingIntegration
  from sentry_sdk.integrations.loguru import LoguruIntegration
  sentry_sdk.init(
  integrations=[
  LoggingIntegration(capture_sentry_logs=True),
  LoguruIntegration(capture_sentry_logs=True),
  ],
  )

  If you had enable_logs set to False:

  • If you were using it to gate usages of the sentry_sdk.logger.X API, you'll need to remove the calls entirely or define a before_send_log callback to filter out unwanted logs.

  If you has enable_metrics set to False:

  • Any metrics emitted using the metrics API will be emitted. You'll need to drop them in a before_send_metric or remove the calls to the API.

  Why We're Doing This

  We recognize this is a disruptive change for some folks and want to make it clear this is a one-off. We're removing the options because they were an unnecessary hurdle that one had to jump through to be able to use logs and metrics, and it was confusing why the logging API would not just work on its own. On the other hand, we wanted to give you more fine-grained control over automatic collection.

New Features ✨

Other

• Set the segment source on the scope for NoOpStreamedSpan by @​alexander-alderman-webb in #7163
• Remove early return for NoOpStreamedSpan in set_transaction_name() by @​alexander-alderman-webb in #7164
• Set the segment name on the scope with NoOpStreamedSpan by @​alexander-alderman-webb in #7162

Bug Fixes 🐛

• (batcher) Add global flush trigger based on the span number by @​alexander-alderman-webb in #7150

... (truncated)

• c819e66 Update README
• 90446df Update CHANGELOG.md
• cb2499c release: 2.68.0
• 1c3b50d ref: Flush trace buckets when segment spans finish (#7170)
• c200bdf test(django): Remove dead code and stale markers from the Django test suite (...
• 4e4ea83 ref(boto3): Move crumbs to integration (#7165)
• 0f0cd1f ref(stdlib): Move crumbs to integration (#7161)
• 2fef9bc chore: Make enable_logs, enable_metrics no-op (#7177)
• 8177739 ref(httpx,httpx2): Move crumbs to integrations (#7149)
• e4d7398 ref(pyreqwest): Move crumbs to integration (#7148)
• Additional commits viewable in compare view